Skip to main content link. Accesskey S
  • Help
  • HCL Logo
  • HCL Sametime wiki
  • THIS WIKI IS READ-ONLY. Individual names altered for privacy purposes.
  • HCL forums and blogs
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
Search
Community Articles > Sametime Proxy > Configuring the ST Proxy server to only connect to specific Community servers in a Sametime Community
  • Share Show Menu▼
  • Subscribe Show Menu▼

Recent articles by this author

Community articleConfiguring the ST Proxy server to only connect to specific Community servers in a Sametime Community
Added by ~Karl Xanapulakoi | Edited by ~Karl Xanapulakoi on May 31, 2013 | Version 2
expanded Abstract
collapsed Abstract
Configuring the ST Proxy server to only connect to specific Community servers in a Sametime Community
Tags: ST Proxy, Sametime Cluster, Community, Sametime Community

Configuring the Sametime Proxy server to only connect to specific Community servers in a Sametime Community

In some deployment scenarios - it may be desirable to have the STProxy server only communicate with certain members of a community cluster - The current 'clusterlist' item in the stproxyconfig.xml file does not allow for this.

The clusterlist works by comparing the name of the cluster a given server belongs to with the names in the list - if there is a match, the server is added to the 'available' list, otherwise not.

In a scenario where there is no Community Cluster defined - each server's 'cluster' is its own CN (cn=server/o=org) - so you can define which individual servers to access using it. As soon as a cluster is defined, the clustername is what is compared.

This workaround extends this by adding a second check against the servers FQDN (community.server.com) and adding any matches to the available list.

To determine the appropriate hostnames to add, review the systemout files from the Sametime Proxy server logs looking for a section similar to:

[9/3/11 0:30:15:767 EDT] 00000026 STConfigurati I com.ibm.rtc.stproxy.server.config.STConfigurationReader Community Server: groupPath: \SametimeCommunity\Cluster\Servers\stcluster\chat.company.com\STIM01WIN.COMPANY.COM
serverFQDN: STIM01WIN.COMPANY.COM
cluster: stcluster
serverURL: 192.168.1.2
[9/3/11 0:30:15:783 EDT] 00000026 STConfigurati I com.ibm.rtc.stproxy.server.config.STConfigurationReader Community Server: groupPath: \SametimeCommunity\Cluster\Servers\stcluster\chat.company..com\STIM02WIN.COMPANY.COM
serverFQDN: STIM02WIN.COMPANY.COM
cluster: stcluster
serverURL: 192.168.1.23
[9/3/11 0:30:15:783 EDT] 00000026 STConfigurati I com.ibm.rtc.stproxy.server.config.STConfigurationReader Community Server: groupPath: \SametimeCommunity\Cluster\Servers\stcluster\chat.company.com\STIM03WIN.COMPANY.COM
serverFQDN: STIM03WIN.COMPANY.COM
cluster: stcluster
serverURL: 192.168.1.14
[9/3/11 0:30:15:783 EDT] 00000026 STConfigurati I com.ibm.rtc.stproxy.server.config.STConfigurationReader Community Server: groupPath: \SametimeCommunity\Cluster\Servers\stcluster\chat.company.com\STIM04WIN.COMPANY.COM
serverFQDN: STIM04WIN.COMPANY.COM
cluster: stcluster
serverURL: 192.168.1.119
[9/3/11 0:30:15:783 EDT] 00000026 STConfigurati I com.ibm.rtc.stproxy.server.config.STConfigurationReader Community Server: groupPath: \SametimeCommunity\Cluster\Servers\stcluster\chat.company.com\STIM05WIN.COMPANY.COM
serverFQDN: STIM05WIN.COMPANY.COM
cluster: stcluster
serverURL: 192.168.1.120

And add the 'serverFQDN' of the server(s) you want to have the STProxy connect to(seperated by a comma) to the 'clusterlist' definition in the stproxyconfig.xml file(s) on your stproxy servers -

STIM03WIN.COMPANY.COM,STIM05WIN.COMPANY.COM

and restart the Sametime Proxy servers.

expanded Attachments (0)
collapsed Attachments (0)
expanded Versions (4)
collapsed Versions (4)
Version Comparison     
VersionDateChanged by              Summary of changes
4Jul 22, 2013, 5:40:57 PM~Lorraine Kiwezen  Minor change
3Jul 22, 2013, 5:37:50 PM~Olga Eltumitherader  Add hotfix number and verbatim tags so text is correctly displayed.
This version (2)May 31, 2013, 12:10:58 AM~Karl Xanapulakoi  
1May 30, 2013, 8:47:41 PM~Karl Xanapulakoi  
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedAbout
  • HCL Software
  • HCL Digital Solutions community
  • HCL Software Support
  • BlogsDigital Solutions blog
  • Community LinkHCL Software forums and blogs
  • About HCL Software
  • Privacy
  • Accessibility